home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Grab Bag
/
Shareware Grab Bag.iso
/
096
/
colosus1.arc
/
COLOSSUS.DOC
< prev
next >
Wrap
Text File
|
1985-12-29
|
134KB
|
3,565 lines
C O L O S S U S
THE "STATE OF THE ART" BULLETIN BOARD SOFTWARE
FOR THE
IBM PERSONAL COMPUTER
COPYRIGHT (C), 1985 BY THE FORBIN PROJECT
DECEMBER 22th, 1985
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
TABLE OF CONTENTS PAGE
1.0 INTRODUCTION 1
1.1 IMPORTANT NOTICE 1
1.2 DISCLAIMER 1
1.3 COPYRIGHT NOTICE 2
1.4 CREDITS 2
1.5 SPECIAL THANKS 2
2.0 COLOSSUS HARDWARE REQUIREMENTS 3
2.1 MODEMS 3
2.2 MODEM SWITCHES 3
2.3 NUMERIC RESULT CODES 3
2.4 MODEM INITIALIZATION 4
3.0 COLOSSUS FILES 5
3.1 SYSTEM FILES 5
3.2 HELP FILES 5
3.3 MENU FILES 5
3.4 MESSAGE FILES 6
3.5 WELCOME FILES 7
3.6 BULLETIN FILES 7
3.7 USER INTERFACE FILES 7
3.8 OTHER SUPPORT FILES 8
3.9 BACKUP FILES 10
4.0 THE COMMAND LINE 11
4.1 DEFINITIONS 11
4.2 EXAMPLES 14
4.3 BATCH FILES 15
5.0 GETTING STARTED 16
5.1 DEFAULT DRIVE 16
5.2 CONFIG.SYS FILE REQUIRED 16
5.3 RUNNING COLOSSUS THE FIRST TIME 16
5.4 SETTING UP THE SYSTEM FILES 18
5.5 SETTING COLOSSUS' ENVIRONMENT 19
6.0 USING THE QUESTIONNAIRE 20
7.0 COLOSSUS NETWORKING 23
7.1 NET-MAIL DESCRIPTION 23
7.2 GETTING A NET/NODE NUMBER ASSIGNED 24
7.3 HOW IS THE NET/NODE SYSTEM ORGANIZED? 24
7.4 NET-MAIL OPERATION 25
8.0 THE FUNCTION KEYS 27
8.1 DEFINITIONS: 27
9.0 THE ALT KEYS 29
9.1 AVAILABLE KEYS 29
9.2 DEFINITIONS 29
10.0 EXTENDED KEYS 34
10.1 AVAILABLE KEYS 34
10.2 EXTENDED KEYS EXPLAINED 34
11.0 THE SCHEDULER 35
11.1 HOW TO ACCESS THE SCHEDULER 35
11.2 SCHEDULES EXPLAINED 35
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
TABLE OF CONTENTS PAGE
12.0 MAIN MENU EXPLAINED 36
12.1 MAIN MENU EXAMPLE 36
12.2 EXPLANATION 36
13.0 MESSAGE MENU (MMS) EXPLAINED 39
13.1 MESSAGE MENU EXAMPLE 39
13.2 EXPLANATION 39
13.3 SPECIAL COMMANDS FOR SYSOP STATUS 40
14.0 FILE MENU EXPLAINED 41
14.1 FILE MENU EXAMPLE 41
14.2 EXPLANATION 41
15.0 SYSOP MENU EXPLAINED 43
15.1 SYSOP MENU EXAMPLE 43
15.2 EXPLANATION 43
16.0 THE SYSOP'S "UPDATE MENU" EXPLAINED 46
16.1 UPDATE MENU EXAMPLE 46
16.2 EXPLANATION 46
17.0 COLOSSUS TECHNICAL REFERENCE INFORMATION 48
17.1 RECORD STRUCTURE FOR "USERS.BBS" 48
18.0 SUPPORT PROGRAMS FOR COLOSSUS 49
18.1 MERGER 49
18.2 RBBS2COL 49
18.3 CALLRPT 50
19.0 LATEST COLOSSUS UPDATES 51
19.1 COLOSSUS PROGRAM UPDATES 51
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
1.0 INTRODUCTION
Colossus is a bulletin board program written in Borland's Turbo
Pascal. Designed on an IBM Personal Computer, Colossus is
compatible with the IBM PCjr and other IBM "Compatibles" like
the Tandy 1000.
Colossus is distributed under the "Userware" concept. You are
encouraged to distribute this software to others as long as you
DO NOT charge, in any shape or form, for this program.
1.1 IMPORTANT NOTICE
Thank you for taking the time and expense to obtain Colossus.
We're sure after you've had a chance to look Colossus over,
you'll agree it is a powerful bulletin board program which
combines both speed and finesse.
This program, like many others, is distributed under the
"Userware" concept. Since Colossus is not a program which
appeals to a mass market, like a communications program for
example, we depend on you --- the lonely sysop --- to support
our undertaking.
It's important to note that very few users of Public Domain
programs ever actually send the author their registration or
donation. Being a sysop, your rewards for running your board
are often a simple "thanks". I hope after you've used Colossus,
and have chosen it over the many other programs available,
you'll show your support with a simple donation.
We could have offered gimmicks like full documentation,
telephone support, etc., in exchange for registration. We
didn't. Instead, we're depending on you, the Sysop, to help
keep our program growing by showing your support and sending in
your registration. Many of you will have Colossus running 24
hours per day, 7 days per week. This is more than any other
program you'll use, and during that use, we're confident we'll
earn your support.
Registration is easy. Send a $50.00 (or more) donation to:
The Forbin Project
715 Walnut Street
Cedar Falls, Iowa 50613
Attention : The Colossus Fund
In any case, feel free to distribute Colossus and to send us any
comments or suggestion via net mail.
1.2 DISCLAIMER
The Forbin Project and all other authors associated with the
writing or evolution of Colossus shall not be held responsible
for any damage incurred by the user to hardware, software, or
peripheral devices while running Colossus. All responsibility
lies with the user of the software.
-1-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
1.3 COPYRIGHT NOTICE
Colossus is Copyright (C) 1985 by The Forbin Project.
Colossus and affiliate programs distributed with it are not to
be modified or distributed without the express written consent
of The Forbin Project.
Colossus is NOT to be sold or used for or with illegal intent
under the penalty of law.
1.4 CREDITS
The Forbin Project's Colossus Development team consists of the
following individuals:
John Friel III, Jim Harrer, Scott Hunter, Dan P. Plunkett
---------------------------------------------------
Many hours have been spent in the development of Colossus --
finding bugs, changing formats, and testing things like the
Networking and File areas. A lot of dedicated people have run
up a lot of healthy phone bills just so Colossus could be
brought to you.
We would like to mention some of those people here:
o Rick Heming of KernCom
o Jesse Levine of Atlantic Palisades
o Tom Neff of Atlantic Palisades
o Plus the many other BETA TESTERS!
Thanks, guys, for your help!
1.5 SPECIAL THANKS
The following sysops have registered their copies of Colossus by
sending in the $50.00 donation. We wish to thank them publicly
for their support. If it weren't for them, we might just say,
"The Hell with it, let's go chase some girls." (Not that we
don't do that now, mind you, but we could be spending more time
mastering the craft!)
SYSOP NAME BOARD NAME PHONE NUMBER
Jesse Levine Atlantic Palisades 718/238-7855
Please Support these boards with you calls.
Pretty short list, huh? Wouldn't you sleep a lot better at
night if your name were added to it?
-2-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
2.0 COLOSSUS HARDWARE REQUIREMENTS
The following are considered the minimum "Baseline" requirements
for running Colossus:
A. 128K Memory
B. One Disk Drive
C. Modem
D. Monitor
2.1 MODEMS
Colossus automatically determines your incoming callers' baud
rates. In order for this to work, your modem must be able to
send numeric result codes, support the Hayes Command Set, and
support DTR (Data Terminal Ready).
The following modems have been tested to work with Colossus and
are believed to be compatible:
A. Qubie Internal/External
B. Rixon PC212A Internal/External
C. US Robotics Courier 2400 & Model 312
D. All Hayes
E. Prometheus
2.2 MODEM SWITCHES
Your modem switches should be set as follows:
1. DTR Normal (UP)
2. Display numeric result codes (Down)
3. Result codes displayed (Down)
4. Modem does not echo. (Down)
5. Auto answer is on. (UP)
6. Carrier Detect is Normal. (UP)
7. Single phone line. (UP)
8. AT Command set is normal. (Down)
9. Escape Code (+++) will not disconnect. (Down)
The above settings are provided for reference only. The numbers
and positions of your modem switches may differ.
2.3 NUMERIC RESULT CODES
Colossus determines the baud rate of incoming calls by receiving
the numeric result code from your modem when the modem
establishes carrier detect. Check your (Modem) owner's manual
for these numeric codes. As space permits we will list the
codes for some of the more popular modems below.
Note that these codes need to be placed in your Colossus
configuration file when you run Colossus. Colossus defaults to
the ARK 2400 codes listed below:
-3-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
USR COURIER 2400: ARK 2400 :
300 Baud # 1 300B # 11
1200 Baud # 5 1200B # 5
2400 Baud # 10 2400B # 10
NOTE: Some modems require that their "extended" result codes be
initialized before they will display different result codes for
connection between 300, 1200 and 2400 bauds. Some Hayes modems
require an ATX1 sent to the modem. Therefore, if you are using
this modem, you MUST place the ATX1 command in your MODMINIT.BBS
file! See below.
2.4 MODEM INITIALIZATION
Colossus automatically sends an "ATZ" pauses 1.5 seconds and
then sends an "AT" to initialize the modem after each call.
This procedure seems to work fine for most modems. However, for
internal modems, or modems that require an "extended" result
mode, this procedure will not work. For this reason, Colossus
allows the sysop to send a special initialization string to the
modem INSTEAD of the "ATZ" and "AT" noted above.
Colossus will look for a file called "MODMINIT.BBS" in your main
Colossus directory. If the file is found, Colossus will read
each line and send that line to the modem until it encounters an
End-of-File.
A "MODMINIT.BBS" file might look like this:
ATZ { Resets the Modem }
ATM0 { Turns off the Speaker }
ATX1 { Turns On Some modems "Extended" result
codes}
ATS0=1 { Answer Modem on first ring }
ATVO { Forces Numeric Result Codes }
ATS7=60 { Set number of seconds the modem will wait
for carrier }
Any legal command YOUR modem will accept will work in the
environment. I can't stress enough that you CONSULT YOUR
MODEM'S OPERATING MANUAL to see what special commands it may
need.
-4-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
3.0 COLOSSUS FILES
There are two types of files that comprise Colossus and allow it
to function.
The first type is SYSTEM FILES. System Files are mandatory for
Colossus's operation and MUST reside in your main Colossus
directory or on the RAM disk from which you run Colossus. These
files are accessed frequently by Colossus during program
operation.
The second type is SUPPORT FILES. Though these files are not
required to run Colossus, I'm sure you'll find them invaluable
in your operation.
3.1 SYSTEM FILES
COLOSSUS.COM - Main System Program
COLOSSUS.000 - 1st System Overlay File
COLOSSUS.001 - 2nd System Overlay File
COLOSSUS.002 - 3rd System Overlay File
NOTE: Overlay files MUST be located in the Colossus Root
Directory along with other System files. Overlay files are used
to store Functions and Procedures which Colossus can call at any
time. They are not held in memory all the time and therefore
must be available for use.
3.2 HELP FILES
You may edit these to fit your personal taste.
MAIN .HLP - Main Menu Help File
MMS .HLP - Message Menu Help FIle
FILES .HLP - Files Menu Help File
SYSOP .HLP - Sysop Menu Help File
PROTOCOL.HLP - Extra help with Uploads/Downloads
3.3 MENU FILES
Menu files contain all the information needed for Colossus to
dynamically build each caller's Menu, dependent on his security
level.
Colossus displays a function only if a caller's security level
is high enough to access it. Therefore, a caller doesn't
necessary see every possible choice in a given menu. This
places you in control and allows you to tailor your board for
your individual needs.
The format used for Menu file entries is:
Command Letter, Command Description,,Security Level,
Command Identifier
Knowing the above, let's use the following example:
B,<B>ulletins,,5,A
-5-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
--- The "B" is the Command Letter. This will be the
letter your caller must type to access Bulletins.
--- "<B>ulletins" is your Command Description. This is
how your file entry will be displayed in your menu on the
screen.
--- "5" is the minimum Security Level required to for the
caller to access this function...or even see it!
--- "A" is the Colossus Command Identifier (CCI) and
should NEVER be changed. The CCI is constant in
Colossus's programing. This letter will be different for
every command.
With one quick look, you'll realize that Colossus allows you to
design your menus to suit your own personal taste.
There are only two rules:
You CANNOT change the Command Identifier (CCI)!
You CANNOT assign the same Command Letter to two commands
in the same menu!
Therefore, if you wanted, you could change Bulletins to read:
P,<P>eg Board,,5,A
Or, Better yet...
A,<A>nouncements,,5,A
Just remember: NEVER change the CCI (the last character on each
entry line), and NEVER use a Command Letter more than once in
each menu.
Colossus uses the following Menu Files:
MAIN .MNU - Main Menu
MMS .MNU - Message Menu
FILES .MNU - Files Menu
SYSOP .MNU - Sysop Menu
UPDATE.MNU - Sysop System Menu
You can use EDLIN, or any word processor that can create ASCII
files, to edit these files.
3.4 MESSAGE/USERS FILES
The following files are used as system files by Colossus. If
they are not found, Colossus will create them.
MESSAGES.BBS - All messages are contained here.
MESSAGES.PTR - Message pointers for scans, etc.
USERS .BBS - Users profile & statistics
-6-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
3.5 WELCOME FILES
To create these files, you can use your favorite word processor,
EDLIN, or any of several programs designed to make Graphic
Welcome Screens.
Even though these files are not mandatory, they give your board
originality.
WELCOME1.BBS - The screen displayed when callers first
connect.
WELCOME2.BBS - The second screen displayed after your
caller logs-in.
NEWUSERS.BBS - Displayed to new users on their first
call.
3.6 BULLETIN FILES
Bulletin files are designed the same way the welcome files are
created, using either EDLIN or a word processor.
BULLETIN.BBS - Main Bulletin screen, lists the
available bulletins.
BULLETx - Where x = 1 - 32767. This number
should correspond to your bulletin
listed in BULLETIN.BBS
3.7 USER INTERFACE FILES
These files are used to help the sysop interface with
users in an efficient manner.
[1..?] .BBS - This special feature was added so the
sysop could send a SPECIAL MESSAGE to an
individual user.
Example: John Doe is User Record number
128 on your system. If you have a file
called "128.BBS", Colossus will dump
and erase this file right after
Welcome2.BBS is displayed the next time
John Doe calls. Your callers log will
have a notation that the special
message was sent.
LIMITS .BBS - If you would like to set different
DAILY time limits according to the
user's security level, you want to use
this file.
The syntax is : Security Level, Daily
Time <RET>
-7-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
Example:
5,10 { 5 Security, 10 Minutes/Day }
10,20 { 10 Security, 30 Minutes/Day }
25,30 { 25 Security, 30 Minutes/Day }
RATIO .BBS - It's seldom (if ever), a caller's
uploads exceed his downloads.
That's par for the course. However,
some users get in the habit of take,
take, take, and NEVER give a thought
to uploading. This file works when /Bx
is set on the command line. It will
display your words of wisdom when this
situation presents itself.
ALIAS .BBS
ALIAS2 .BBS - ALIAS.BBS contains a list of all names
you don't want to allow on your board.
Names like: The, Hacker, Dr., Mr., PC,
Killer, Etc.
Colossus reads this file line-by-line
and compares the names in the file
against the caller's first and last
name. If a match is found, then
ALIAS2.BBS is dumped to the screen and
the caller is logged off!
3.8 OTHER SYSTEM FILES
You may also add the following files to your system:
EDTORIAL.BBS - File which is shown to callers when
they request the Editorial from the
main menu.
GOODBYE .BBS - This file is displayed when a caller
logs off the system.
FILES .BBS - Used in the File Sub-Directory for
listing files available for download in
that area. (See "Creating File Areas")
QUOTES .BBS - Quote for the day for your callers
during log-on. Colossus indexes this
file, searching for a blank line
between each quote.
ALT-A .BBS - ALT+A dumps this file to the screen, logs
the caller off, and LOCKS him out on
future calls. Works great on problem
callers. (Jim's favorite).
-8-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
NO300 .BBS - Dumps this file to 300 baud callers, when
300 baud callers are not allowed.
Displayed only when /3 is on the Command
line.
C .BAT - Batch file used to invoke Colossus.
Also contains the necessary commands
for sysop's remote drop to DOS.
REMOTE .BAT - Required if you want to drop to DOS
from remote.
SHELL .BBS - This file must contain a list of your
programs available from the <O>nline
Programs command. See Section 12.2.
F8 .BAT - This file is dumped to the screen when
you terminate a call. Could say:
"Sorry, the sysop needs the computer!
Please call back later!"
MAILER .LOG - Contains all your Net-Mail activity.
MODMINIT.BBS - This file is sent to "initialize your
modem" after each caller. See Section
2.4
PAGED .BBS - Displayed when a caller pages the
sysop, who either has the page feature
turned off, or simply doesn't answer
the page. The file could contain your
office hours, or suggest that the
caller leave a message or comment.
ABOUTCOM.BBS - Some sysops have special policies about
not replying to Comments to the Sysop.
This is because the sysop normally
has to write down the caller's name
and question, exit Comments, and
move to the Messages Section, just to
enter a reply. (Whew.).
As an alternative to all that labor,
this file can be displayed when a
caller selects <C>omments at the
Main Menu.
3.8a ABOUT DISPLAY FILES
As you can see, Colossus allows you complete flexibility when it
comes to displaying files. The sysop has nearly total
flexibility in making his board as unique as he wants.
There are a couple of features built into the display file
routines which give you even more control. They are:
CTRL-B - Toggles More Prompt.
-9-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
CTRL-C - Toggles the callers' ability to interrupt the
screen with Ctrl-K or Ctrl-C.
Place these characters in your display file. Remember it works
like a toggle. When Colossus sees the first one, it turns the
function OFF and leaves it OFF until it sees another toggle.
Colossus defaults to Interrupt ON and Screen <M>ore Prompt ON.
3.9 BACKUP FILES & CRITICAL LOGS
When you perform sysop maintenance like Packing the Message Base
or Packing the Users file, Colossus will first make "Backup"
copies for you. You don't need to have these files in your
Colossus root directory after they're made. If space is a
problem on your board you could copy the backups to disk or
discard them. They are:
MESSAGE.PBK - Message Pointer Backup File
MESSAGE.TBK - Message Base Backup File
USERS .BAK - Users Backup File
Colossus also keeps track of critical errors incurred during
program operation. These are stored in a file called
"CRITICAL.LOG".
If you're having problems running Colossus, and you're sure
you've tried everything, report your version number and all the
information included in your CRITICAL.LOG file to the Beta
tester nearest you, or to Colossus Country. We'll do everything
possible to correct the problem or explain to you why you're
getting the errors!
-10-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
4.0 THE COMMAND LINE
The Command Line (CL) can be used to make Colossus start-up with
different parameters.
The Command Line and its various parameters are what you type at
the DOS Prompt (or send to the program from a batch file) when
you boot Colossus.
/C - Define the CD Mask
/D - Set the Daily Time Limit
/F - Set the Time Limit for New Users First Day
/L - Set Logon Time Limit (time per logon)
/K - Set Daily Download Limit in amount of K
/2 - Use the Com2 Port
/P - Mandatory first-time caller Phone Number
/R - Invoke a Pre-Registered System
/W - Allow Sysops to drop to DOS
/S - Default Security Level
/Q - Mandatory first-time caller Questionnaire
/U - Activate your Quote file at sign-on
/3 - Disallows 300 baud callers
/M - Modem Type
/I - Initialize the Modem (For Ark Modems)
/O - Allow time compensation for Uploads
/B - Download/Upload Ratio Warning
/Z - Seconds the modem waits for Carrier Detect.
4.1 COMMAND LINE PARAMETERS EXPLAINED:
/Cx (x=1,2,4,8,16,32,64,128,256)
--------------------------------
This Switch tells Colossus where the Carrier Detect Bit [CD] is
located on your modem. If you have one of the KNOWN supported
modems listed in the Hardware Needs section, do not use this.
First, try Colossus without this option. Then, if it does not
answer the phone when called, find out your CD MASK, and put it
in. Colossus defaults to 128, which is used on the more popular
modems. A CD carrier detect bit located at bit 64 would be:
COLOSSUS /C64
/Dx (x=1 to any #)
------------------
This switch sets the Daily Time Limit for all callers. The
default Daily Time Limit is 60 minutes. If a user uses all of
his Daily Time Limit for a particular day, he will be logged off
and will not be able to log back on that day. If a user has a 60
minute Daily Time Limit, he could sign on the system as many
times as he wanted until the 60 minutes was used up, or until a
day had passed. The following will set the Daily Time Limit to
100 minutes:
COLOSSUS /D100
-11-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
/Fx (x=1 to any #)
------------------
The /Fx switch sets the New Users First Day Time Limit. If you
wish a new caller to have a lower time limit, then you can set
that time with this switch. If you wish, you can set the New
Users Caller Limit the same as the Logon Limit [see below] so a
new user has the same amount of time as a veteran caller. If
the Fx switch is not used, then it is automatically set to 30
minutes. The following will set the New Users First Day Limit
to 45 minutes:
COLOSSUS /F45
/Lx (x=1 to any #)
------------------
This switch sets the Time Limit per Logon. If the Daily Limit is
set to 100 minutes, and the Logon Limit is set to 50 minutes,
the user could use 2 full log-logons. This means a user can use
100 minutes that day, but only 50 minutes maximum for each
logon. If this parameter is not used, the Logon Time Limit will
default to 45 minutes. The following will set the Logon Time
Limit to 86 minutes:
COLOSSUS /L86
/Kx (x=1 to any number)
-----------------------
This switch sets the amount (in thousands of bytes [K]) a user
may download in one day. If he exceeds his limit, he will not
be able to download any more files that day. If this parameter
is not used, the K Limit would be set to 1000. The following
will set the K Limit to 200k.
COLOSSUS /K200
/2
--
If used, this switch will tell Colossus to use the Com2 port.
Only use this if your modem is installed on Com Port 2.
/P
--
This switch will set Colossus to ask all first-time callers for
their home phone numbers.
/Rx (x=Nul, 1, 2, or 3)
-----------------------
This switch will set Colossus to function as a RESTRICTED
system. There are also 4 options to set up a restricted system.
Here is a list of the available options for the /R command:
Nul(just enter /R): Restricted System.
-12-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
1 : First-Time Caller is forced into to leave a comment
when he gets to the Main Menu (but he can <A>bort it w/o
leaving one).
2 : First-Time Caller is forced to fill out a
Questionnaire when he gets to the Main Menu.
3 : Immediate log-off
/W
--
This switch allows remote sysops to drop to DOS. By invoking
this switch, a remote sysop can sign on his own system and, by
entering a specific command, can then drop to DOS.
/S
--
This switch allows the sysop to set his default Security Level
for First-Time Callers. The default security level is 5 if this
switch is not used. The entry below would set a user's security
level to 12 upon signing on for the first time:
/S12
/Q
--
Using this switch will force a first-time caller to fill-out a
questionnaire before entering the system. This is an option for
use on a RESTRICTED system, but can be used with a Public System
as well.
/U
--
Activates QUOTES.BBS. This file displays a different quote-for-
the-day each time a user signs on.
/3
--
If you want to limit your board to callers with 1200 or higher
speed modems, you can restrict access so that 300 baud callers
receive a message "300 baud is not allowed at this time". Also,
if you have the file 300.BBS available, that file will be dumped
to the screen.
/Mx (x=1, 2, or 3)
--------
One of the toughest obstacles we have had to overcome is dealing
with all the different modems. For this reason, we have had to
make Colossus flexible enough to work with a broad range of
modems. The /M parameter helps provide that flexibility.
If there is no /M switch on the Command Line, Colossus defaults
to answer by ring-detect and determines baud rate by the numeric
-13-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
result code it receives from the modem. These settings can be
altered, however, with the following switches:
/M1 = Answer by ring detect, determine baud by C/R's.
/M2 = Answer by Carrier Detect, determine baud by Numeric
result codes.
/M3 = Answer by Carrier Detect, determine baud by C/R's
NOTE: As our experience grows with all the different modems
available, we gain the ability to add special modem commands to
fit your needs. If you can't get your modem to respond
correctly, tells us about your modem type, and we'll try to
help!
/I(300,1200,2400)
-----------------
Ark 2400 Modems must me initialized at 2400 baud in order for
them to receive 2400 baud calls. Therefore, we have added a
switch to do this. As we have more experience with all the
different modems, we may learn that this switch is or is not
needed for modem brands other than ARK. ARK 2400 owners must
put the following on the command line:
/I2400
/Ox (X = 1,2,3..32767)
----------------------
Allows Time Compensation for uploads. With /O1 set callers will
receive 1 minute credit for every 1 minute spent UPLOADING.
With /O2 the caller would be credited 2 minutes for every one,
etc.
/Bx (X = 1,2,3..32767)
----------------------
This feature will warn the caller that their Download Ratio is
Too High. If /B5 is set, then callers will be warned when they
have downloaded more than 5 files to everyone they uploaded.
This switch must be on the command line if you wish "RATIO.BBS"
to be displayed after the warning.
4.2 COMMAND LINE EXAMPLES
A>COLOSSUS /D60 /L40 /K350 /P
These switches can be used in any order, and none need be used.
The Command Line above would set your system [in order] for a
60-minute Daily Time Limit, 40-minute Logon Limit, 350k download
limit, and a First-Time Caller must enter his phone number
before entering the system. Enter your command line from the DOS
prompt or from a batch file. (See below.)
-14-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
4.3 BATCH FILES
It is advisable to use a batch file when running Colossus. Here
are some advantages:
- If an error occurs, it will reset with a batch file
- If there is an power outage, batch files could set up
Colossus again.
- Prevents errors and cramped fingers when typing the
Command Line
Of course, batch files are not a MUST, but we recommend them. I
use a batch file called C.BAT on my system that invokes
Colossus; it consists of the following commands:
CTTY CON
COLOSSUS /S10 /D100 /L60 /F45 /W
IF ERRORLEVEL 32 BACKUP.BAT { Used with Schedule "X" }
IF ERRORLEVEL 16 REMOTE.BAT { For Remote Drop to DOS }
C.BAT
This will set Colossus up with the proper parameters we
discussed in the Command Line section, and, if for any reason
Colossus drops to DOS, it will reboot itself. Batch files can be
named any legal DOS name, but must have a .BAT extension.
-15-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
5.0 GETTING STARTED
If you're like I was, what you really want to do is put the
documentation aside, and get started running Colossus. Well,
let's do just that. As you begin to get comfortable with the
operating system, you can refer back to this guide to explain in
further detail some of the features available in Colossus.
5.1 DEFAULT DRIVE
If you're using a floppy-based system, then you'll want to have
all the Colossus files located in drive A. Later, after you
learn your way around, you can set up Colossus so the overlays
and other files can be located in a RAM Disk. But for now,
let's have all the files resident on drive A.
If you're running from a hard disk, then make a main sub-
directory for Colossus. Place all your Colossus files in this
sub-directory.
5.2 CONFIG.SYS FILE REQUIRED
As you begin running Colossus, we feel you'll quickly agree it's
lightning FAST! Colossus is a complicated Communications
program which requires several files being opened at the same
time. For this reason, you'll need to have the following files
and buffers set in your computer's CONFIG.SYS file, located in
your root directory. If you are unfamiliar with how CONFIG.SYS
works, consult your DOS manual, or ask any Colossus Beta
Testers.
NOTE: Colossus WILL NOT work properly if this is not done!
CONFIG.SYS should have the following settings:
FILES=20
BUFFERS=50
5.3 RUNNING COLOSSUS THE FIRST TIME
After you have all the Colossus files located on your default
drive, all you have to do to get things running is type:
"Colossus" at your DOS prompt. Don't type the quotes! Your DOS
command line should look like this:
A>Colossus
Then, press RETURN.
The first thing you see is the registration screen -- you have
registered your copy haven't you? (If not, or if you've lost
the address to send your 50 bucks, we remind you here!)
For a quick listing of your keyboard commands press HOME. The
help screen will appear.
-16-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
Next you'll see Colossus loading up and building your System
files. When you see the prompt "Colossus ready for calls
at....", the program is ready to run. Almost.
First, though, let's set up your configuration file. This is
done by holding down the ALT key AND pressing the F key (we
refer to this action as ALT+F). You should see the
configuration menu:
Parameter Default
1. Messages must be proofed before users can read them.....No
2. Batch (Telink) protocol is available to users..........Yes
3. Colossus Node #..........................................0
4. Colossus Net #...........................................0
5. Alternate Node #.........................................0
6. Alternate Net #..........................................0
7. Should Colossus make long-distance calls at mail time?..No
8. All messages must be public.............................No
9. Security level to be considered a SYSOP.................50
A. Character (s) returned for 300 baud connect.............11
B. Character (s) returned for 1200 baud connect.............5
C. Character (s) returned for 2400 baud connect............10
D. Filename to write automatic call analyzer output to..ANALYZER.BBS
If you need to change any defaults to match your configuration,
see section 9.2 for a complete explanation of this menu.
When you've finished entering all the above information, press
the ESC key to save your changes and return you to Colossus.
Next, to sign-on locally, you need to hold down the ALT Key and
type the letter "S". Colossus will place your modem "Off Hook"
and prompt you for your First Name.
Now, since you're the sysop, you can simply type SYSOP at the
prompt and continue. If you prefer to use your own name then
you can do that, also. Just keep in mind that this is how
you'll be signing on locally to do Sysop Maintenance. Also,
when you send a message, this will be the Name imbedded in the
FROM column in the message area. Let's assume you just enter
Sysop.
Next Colossus prompts you for you last name. Press the RETURN
(or ENTER) key. Now Colossus asks if all the information you've
given it is correct. If so, answer "y."
At the prompt for a password, type in a word you'll never forget
and no one else will ever guess.
Colossus asks you to retype your password for verification. Do
it, and press ENTER again. This will take you to the Main Menu.
At the Main Menu, hold down the Alt key and type the letter "N"
(ALT+N). You should see "Enter New Security Level". At this
point, enter 999. This will give you high enough security level
to access all of the SYSOP Utilities.
-17-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
Now, hit the ENTER key once and you'll see the Main Menu
reappear, this time with the <U>tilities for Sysop listed.
5.4 SETTING UP THE SYSTEM FILES
The very next thing we must do is configure the System files.
Type 'U' at the Main Menu for "Utilities for the Sysop."
Next you'll see the Sysop Menu which includes "<4> Update System
Files."
Select #4 and hit ENTER.
Next, the Update Menu will appear, which looks like this:
Update Menu:
<A>Net message system toggle <B>Net file system toggle
<C>reate/read a system file <D>ownload file path
<F>ile security <I>Message Description
<J>File Description <L>ist system file
<M>essage security <Q>uit to MAIN MENU
<S>ave system file <U>pload Path
Let's start by creating the first system file. This is done by
selecting 'C' for "Create/read a system files".
Colossus will respond with "System Number:". You respond by
typing 1 and return. Colossus will respond with "Creating
System Record #1."
Now to get an understanding of what we're setting up, type L for
"List System File". You'll see the following:
System Record #1
Message security..0
File security.....0
Upload Path.......
Download Path.....
Msg description...
File description..
At this point, some general explanations are in order.
Each system record contains the minimum security level required
for a caller to access the files and message board associated
with that system record.
The Upload & Download path are any legal DOS pathnames telling
Colossus where it can find the files associated with the file
description. You can set uploads to go into a single "Upload
file" area, or to different areas, which you could specify by
subject. Here are a few examples of upload/download paths:
The following would send all the uploads to a sub-directory
called "UPLOADS" and allow the caller to download programs from
a sub-directory called "GAMES". (Note: Colossus is the parent
directory.):
-18-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
Upload Path.......C:\COLOSSUS\UPLOADS
Download Path.....C:\COLOSSUS\GAMES
The next example would send both uploads and downloads to the
same sub-directory:
Upload Path.......C:\COLOSSUS\GAMES
Download Path.....C:\COLOSSUS\GAMES
If you're running on a floppy-based system with your uploads and
download files on drive B, and not using sub-directories, you
could do the following:
Upload Path.......B:
Download Path.....B:
Lastly, you need to enter descriptions for these areas. These
descriptions are displayed when the caller wants to see what
different message and file area available on your board.
Other options include toggling a message or file area for net-
working.
When you're done, and the record is the way you want it, BE SURE
TO SAVE THE RECORD BEFORE CONTINUING ON! Type "S" for save and
hit ENTER.
A system record doesn't need to contain BOTH a File AND Message
area. You can have a File area and no Message board assigned to
that record. Simply set the message security high enough so the
caller can't access it.
5.5 SETTING COLOSSUS ENVIRONMENT
Some of you may want to place COLOSSUS.COM and the overlay files
in a RAM disk. This can be done by setting Colossus'
environment through a DOS call.
The syntax would be :
A> SET COLOSSUS = C:\
Assuming Drive 'C' is the location of your RAM disk. Now you
can place the .COM, .000, .001, .002 files in RAM, and watch it
FLY!
-19-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
6.0 USING THE QUESTIONNAIRE
Colossus uses a simple procedure to generate the Questionnaire.
Questionnaires are simple text files that are interpreted by
Colossus. There is a very simple line-oriented pseudo-language
that interprets these scripts. There are only a couple of
"commands", and only two crude conditionals.
The answers to the questionnaire are put in a separate file,
without the questions. They are also normal ASCII text, but in a
fixed field format with field characters, to make post-
processing of the questionnaire easier.
The questionnaire consists of two files:
QUESTION.BBS The questionnaire script
ANSWERS.BBS The answers
Answers are appended to the end of the answer file; it is
created if it does not exist.
The first character of each line tells Colossus what to do with
the line. This first character is a normal printable character.
If the first character is not one of the known commands, the
line is merely displayed.
The questionnaire commands are:
/<prompt string>
Display <prompt string>, then input a single line of text.
Maximum line length is 78 characters. The usual editing is
available. The inputted text is written to the answer file.
*
Put user info to the answer file: name and last (current) sign-
on time and date. Useful for the "what kind of system ..."-type
questionnaires. Leaving this out allows confidential
questionnaires, as there is no other record of which caller
filled one in.
+N <prompt string>
Multiple choice. The single digit number N is the number of
possible choices (1 - 9). If an illegal number is entered, or
the number is missing, the number of choices defaults to one
(also known as the Soviet Multiple Choice Question), but at
least the system won't hang up. The choice entered by the user
is checked for in range 1 to N, and saved in the answer file.
There is a special feature of multiple choice: an internal flag
is set if the last choice (choice N) is selected, that can be
tested by the ! command, described below.
!
To be used ONLY after a multiple choice question. If the last
choice of a multiple choice was selected, this terminates the
-20-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
questionnaire. Allows asking "Do you want to fill this out (1)
yes (2) no".
_ (Underscore)
Unconditionally clears the conditional flag.
Below is an example of a new user questionnaire:
NEW USER INFORMATION
~~~~~~~~~~~~~~~~~~~~~~
You are required to Register to this System. Please fill
out the following questionnaire.
Your access will be upgraded within 48 hours.
Thank you for your cooperation!
*
+2Have you Registered with Colossus Country Before? (1)No
(2)Yes
!
/ What is your real name (first & last):
/ What is your Street Address:
/ City, State, Zip:
/ What is your voice phone no.:
/ Where did you hear about this board:
/ What is your age:
Your ANSWERS.BBS would contain an ASCII file with the user's
answers to your questionnaire. The answers would look like the
following:
1:-----John Doe
2:1
3:John A. Doe
4:1234 Any Street
5:Any town, ST, 12345
6:805/555-5342
7:KernCom
8:23
Each time the questionnaire was invoked, the answers would be
appended to ANSWERS.BBS. Note, if the caller had answered "2" to
the first question, the questionnaire would have been
terminated.
One of the easiest ways to read your answer files, is to Drop to
DOS (ALT+D) and copy ANSWERS.BBS to your printer. Then you may
exit back to Colossus and not disturb the program's System
Status Report.
If a caller selects <Q>uestionnaire from the Main Menu, and you
do not have a file called QUESTION.BBS in the main Colossus
directory, your caller will receive the following message:
"Sorry, No questionnaire today"
If you are not going to have a Questionnaire on your bulletin
board, we recommend you raise the access level in the MAIN.MNU
-21-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
file high enough so that the prompt will not even show in the
menu. This keeps the screen clean, and will not confuse your
callers (or waste their long distance dollars).
-22-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
7.0 COLOSSUS NETWORKING
Before we get started talking about how Colossus handles its
network system, we must give you a little history about this
process. First, this whole network concept was dreamed up by a
man named Tom Jennings, who, among other things, is responsible
for a bulletin board program called "FIDO". Tom had a wonderful
idea of connecting these bulletin boards together at a
predetermined time to send mail, or packets, to each other. We
thought enough of Tom's idea to include his FIDONET concept in
Colossus.
It's important to note however, that Tom doesn't release his
source of "FIDO", much like Colossus, therefore we simply took
Tom's idea and worked out the code in Turbo Pascal. We have
spent a great amount of time and effort to ensure the two
systems are compatible. Therefore, Colossus can send mail to
Fido nodes and Fido can send mail to Colossus Nodes.
7.1 NET-MAIL DESCRIPTION
(NOTE: Many of the following notes were taken out of Tom
Jennings's "FIDO'S Complete Operating Manual".)
The purpose of this net mail concept is to link Colossus- and
Fido-based Bulletin Board systems together for automatic message
transfers.
This Net system is a true dial up packet switch network system
that supports many different topologies. It supports routing,
message forwarding, scheduling and uses a tuned collision
detection algorithm over normal phone lines, for the lowest
possible cost and highest efficiency.
The simplest scheme, and the one to set initially, supports
point-to-point messages. Most major geographical area have a
host that will accept mail for itself and its local nodes.
After you have contacted any other Colossus (or Fido) sysops in
your area, you can tie into their local network, and take
advantage of the lower cost. Each local area runs things
differently, and their policies cannot be covered here. If you
can't find your local region or host, contact Colossus 200/3 at
805/399-1329, where you can find the latest node list and other
files to help steer you in the right direction.
The original FidoNET design was built around the current
Bulletin Board architecture which is basically: an unknown
number of completely independent, stand alone systems, with
extremely low overhead in both maintenance and cost. The
Colossus Net System was designed to be compatible with this, in
that it should involve:
1. No extra work for the SysOp.
2. No effect on normal BBS operations.
3. No unexpected extra costs.
4. No effect upon system reliability.
-23-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
Colossus handles this totally automatically, and requires no
extra work, once set up. Other than the effect of allowing
Network-wide message traffic, the only other affect upon the
current BBS is that it is "down" to normal traffic (regular
callers) during the National net time of 1am to 2am (PST).
Costs, if any, are controlled by the sysops. Unless
specifically enabled, mail will not be sent out from a node.
Remember, sending mail costs money; receiving packets is free.
Colossus provides accounting and cost limitation functions (all
automatic) to prevent unauthorized mail from being sent. There
can also be "free" traffic to non-toll call nodes as well as
limitations put on long distant calls. The usual privilege
levels can be applied to each of the mail commands, to control
their use.
Net-mail success/failure does not in anyway affect BBS
operations. Failure to make a connection and transmit a packet,
or errors during incoming packets, affect only the mail sent or
received. In the case of transmission, the message will not be
sent, nor will charges (if any) be applied to the sender's
credit account.
For a paying system, the sysop must occasionally set the user's
credit, using the "Utilities for the SysOp" section and
crediting the user's account. If reasonably large sums are used
as a minimum ($5.00 or more), this will not need to be done more
than once every few weeks.
7.2 GETTING A NET/NODE NUMBER
After you have Colossus successfully running you should set your
NET number to 299 and your NODE number to 99. These numbers
indicate your board is currently waiting to be assigned an
official classification, and has been assigned temporary
numbers.
Next, you should call Colossus Country @ 805/399-1329 and read
the bulletin regarding "Getting a Colossus Net & Node Number".
Be prepared to answer the following questions:
1. Board Name 6. City, State, Zip 11. Board's Theme
2. Board Number 7. Hours of Operation 12. Your Age
3. Sysop Name 8. Type of Computer 13.
4. Voice Number 9. Modem Type 14.
5. Address 10. Baud Rates Available 15.
This information will help us to know more about you and your
board, in the event you ever have the need to contact us. This
information is necessary if you wish to be assigned a NET/NODE
number, and if you plan on using the Net-Mail feature. If you
don't want numbers assigned to you, then the above information
is not necessary.
7.3 HOW IS THE NET/NODE SYSTEM ORGANIZED?
After trying to analyze why people use the Net-Mail feature of
Colossus I came up with one common reason: "Location". More
than any other reason, my callers used the system because they
wanted to contact a person in a certain area of the country.
-24-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
For this reason, Nets will be assigned by State. Currently,
Colossus has the following Nets assigned:
Net 200 - Colossus Beta Testers | Net 226 - Michigan
210 - Northern California | 230 -
212 - Southern California | 232 -
214 - Virginia | 234 -
216 - Iowa | 236 -
218 - Texas | 238 -
220 - New York | 240 -
222 - Florida | 242 -
224 - Massachusetts | 244 -
Note, the Colossus Beta Sites are all listed in Net 200. This
is so you have easy access to the one closest to you for help
and assistance, and, should the need arise, a place to report
the ugly bugs! (YUCK.) Therefore, Beta sites will be assigned
two Net/Node numbers, one for their Beta site classification,
and the other for their State location.
Nodes are Systems within each net. Each Net can hold up to
32767 nodes before we have to open another Net number.
7.4 NET-MAIL OPERATION
Within Colossus is the Net-Mail module which is run as specified
by the scheduler. This module is a time driven system, and the
national time slot is at 1:00 AM Pacific Standard Time, 4:00 AM
for you on the east coast. During normal Colossus operation,
users can enter messages, and, during the Net-Mail time, these
messages are made into packets and sent to the right
destination. The messages may be destined to any one or more of
the available remote nodes in the nodelist.
At the predetermined time, the Net-Mail module takes control.
Within 5 minutes of the scheduled event Colossus will
automatically drop DTR so users do not get on the system. If a
user is on the system, Colossus will inform them of the upcoming
scheduled event and give them a chance to log-off, or, if
needed, Colossus will log them off just as if they exceeded
their time limit. The Net-Mail module then (if enabled) creates
mail packets, one per node, containing the messages for each
node. If there is no mail to a node, no packet is created, and
no call is made to that system.
After the outgoing packets are made, Colossus alternately waits
for calls and attempts to place calls. Mail packet transfers
are done on a collision detection basis. After the first few
collisions, the network synchronizes. If there are a number of
nodes to send mail to, each one is called in turn, until all are
sent, or mail time is over. If it fails with one node, it goes
on to the next, and repeats the failed one only after trying all
of the others first.
In between outgoing calls (if any) Colossus delays a random
interval, during which it waits for incoming calls. This
interval, along with the redial algorithm, synchronizes the net
after the initial collisions.
-25-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
If an incoming call is detected, it attempts connection with it.
The baud rate is determined (same as for a normal caller in
Colossus), a message to human callers is displayed (warning them
that the board is accepting only other Colossus or Fido Nodes),
and a synchronization process is started. This process must
complete within 60 seconds, or the call is terminated. Once
synchronized, the packet transfer is made. The receiver just
stores that packet for later use, and then disconnects.
Whenever an incoming call is received, Colossus calls out
immediately afterwards (assuming there are calls to be made),
since there is a high probability that the line is now clear.
This helps synchronize the network.
To place an outgoing call, the sender dials the number, performs
the sync process mentioned above, and transfers its outgoing
packet. (Messages to a given node are again checked against the
node list at mail time; if they do not match, the packet is not
sent, and an error is logged.) If the transfer was successful,
the destination node number is deleted from the sender's list of
nodes to call.
The collision detect algorithm is optimized such that during the
first few minutes of mail time, there are many collisions, after
which the net synchronizes, and none or few collisions occur.
When mail time is over, Colossus deletes all its outgoing
packets that were assembled, and for each one that was sent
successfully, marks those messages (in the mail area) as SENT,
so the originator can tell if they went out or not. Then, the
incoming packets are unassembled, and the messages placed
sequentially in the mail area. These packets are then deleted.
If any mail at all was sent, the user credits are balanced. This
is somewhat unsatisfactory, as it balances the accounts even if
the mail was not sent. This is to prevent extremely long
processing time necessary to account for each message and user.
(Users lists run upwards of 600 entries typically; on a floppy-
based system, this would become unworkable.)
Net-Mail then terminates, and, if there were no fatal errors,
invokes Colossus for another day. Messages received are then
accessible like any other message and placed in the message area
marked for Net-Mail.
All of your Net Activities are recorded in a file called
"MAILER.LOG" which can be viewed with any listing type program
or by using the DOS command TYPE.
-26-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
8.0 THE FUNCTION KEYS
F1 - Take five minutes from user
F2 - Give five minutes to user
F3 - Toggle Printer [on/off]
F4 - Toggle Sysop Available [yes/no]
F5 - Toggle Sysop Page Bell [on/off]
F6 - Toggle Screen Attached [on/off]
F8 - Terminate Caller
F10 - Exit to DOS
8.1 DEFINITIONS:
F1 (Take five minutes from user)
--------------------------------
If a user is ONLINE and you wish to deduct five minutes from his
time left on the system, you can do so by pressing F1. This is
helpful if you want to get on the system and a user has lots of
time left.
F2 (Give five minutes to user)
------------------------------
If a user is ONLINE and you wish to add five minutes to the time
he has left on the system, you can do this by pressing F2. This
is helpful if you want to give a user more time, or you are just
feeling generous that day.
F3 (Toggle Printer [on/off])
----------------------------
All of the information that is written to the CALLERS.LOG file
(e.g. Time on/off, Downloads made, messages written, etc. by
users) will be printed by your printer if 1) You have a printer,
and 2) If you have the Printer Toggle ON. If the Printer Toggle
is ON, the word "Lptr" will appear at your 5-line window at the
bottom of the screen. You can at any time toggle the Printer OFF
or ON by pressing F3.
NOTE: If you have the printer toggled ON, and your
printer is "OFFLINE" Colossus will freeze up, until you
either place your printer "ONLINE" or turn the printer
off. If any of you know how to trap for this in Turbo,
please share your ideas with us!
F4 (Toggle Sysop Available [yes/no]
-----------------------------------
By toggling this parameter [ON or OFF] the sysop can decide
whether or not he can be paged. If the Sysop Available is ON,
the word "Avil" will appear at your 5-line window at the bottom
of the screen. Then the Sysop can be paged. If the Sysop
Available is OFF, the word "Avil" will disappear from the 5-line
window, and a user will not be able to page the sysop. To
toggle it ON or OFF, just press F4.
-27-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
F5 (Toggle Sysop Bell [on/off])
-------------------------------
By toggling this parameter, the sysop can choose whether or not
sound will be made when he is being paged. This function will
only be in use if the Sysop Available is ON. If the Sysop
Available is ON, but the Sysop Bell is OFF, then the sysop can
be paged, but no sound will be made. But if the Sysop Bell is
ON, sound will be made in an attempt to attract the sysop's
attention. To toggle it ON or OFF, press F5.
F6 (Toggle Screen Output [on/off])
----------------------------------
When the Screen Output toggle is OFF, nothing that is fed to the
screen is shown. But if it is ON, everything is shown. This is
handy to have when you go away for a while and there is no
reason to have the screen ON. When you return, you can simply
press F6 and all data will show up on the screen.
NOTE: Your monitor does not have to be ON for Colossus to
run.
F8 (Terminate Connection)
-------------------------
If a user is ONLINE and you wish to disconnect him, simply press
F8 and the connection will be terminated. If you have a file
called "F8.BBS" created, this file will be dumped to the caller.
This file could contain, "Sorry the sysop needed to use the
system. Please call back later."
F10 (Terminate Colossus)
-----------------
Pressing F10 will terminate Colossus.
-28-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
9.0 THE ALT KEYS
Colossus uses the ALT key in combination with a letter key for
many of its commands. Here is a list of the ALT keys used by
Colossus:
9.1 AVAILABLE KEYS
*O* ALT+C - Force a user into Chat Mode
*W* ALT+D - Exit to DOS and load COMMAND.COM
*W* ALT+F - Configure System
*W* ALT+G - Set Caller Number
*A* ALT+K - Keyboard Toggle [on/off]
*O* ALT+N - Changes Callers Security level On line
*A* ALT+S - Sysop Sign-On/Sysop Next
*W* ALT+F - Toggles Sysop increases Caller Count
*O* ALT+A - Screen dumps "ALT+A.BBS" locks caller
out
*A* ALT+R - System Status Report
Key
---
*O* - User must be ON-LINE to perform
*W* - Colossus must be "Waiting for calls" to perform
*A* - Can be used anytime Colossus is running
To use an ALT+Key, the ALT key and the appropriate letter key
must be pressed simultaneously. (First, press down the ALT key,
then, while holding the ALT key down, press the letter key.)
9.2 DEFINITIONS
-----------
*O* ALT+C (Force Chat)
------------------
If used, this ALT+C would force a user into Chat mode. Once
finished in Chat mode, just press CTRL-Z to get out of Chat
mode. A user must be ON-LINE to perform this function.
*W* ALT+D (Drop to DOS)
-------------------
This ALT+Key is VERY useful. When this function is activated,
COMMAND.COM will be loaded into memory, and you will be taken to
the DOS prompt. You then may load any other programs [provided
you have enough memory], or perform any other DOS functions you
care to. You can load up your Qmodem, edit a file, etc. Then,
when you are ready to run Colossus again, just go back to the
drive or sub-directory where Colossus is located, and at the DOS
prompt type EXIT. Colossus will flash back on-screen in the
exact place you left off. A very useful function.
-29-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
*NOTE: You MUST return to the drive and/or sub-directory
where Colossus is located before typing EXIT.
*W* ALT+F (Configure System)
-----
After you activate this function, a configuration menu will
appear. These menu items configure parts of your system. Here
is what the menu parameters are and their defaults:
Parameter Default
1. Messages must be proofed before users can read them.....No
2. Batch (Telink) protocol is available to users..........Yes
3. Colossus Node #..........................................0
4. Colossus Net #...........................................0
5. Alternate Node #.........................................0
6. Alternate Net #..........................................0
7. Should Colossus make long-distance calls at mail time?..No
8. All messages must be public.............................No
9. Security level to be considered a SYSOP.................50
A. Character (s) returned for 300 baud connect.............11
B. Character (s) returned for 1200 baud connect.............5
C. Character (s) returned for 2400 baud connect............10
D. Filename to write automatic call analyzer output to..ANALYZER.BBS
Definitions
-----------
<1> "Proofing Parameter"
------------------------
If set to "No", this parameter will allow users to read mail
that has NOT yet been proofed (read) by the sysop. But if this
parameter is set to "Yes", then every Public message that is
left by a user will be set to Private. Then, after the sysop
has proofed the message to make sure it contains legitimate
information, he can change the message status to public. If a
private message is left by a user to another user, it does not
have to be proofed by the sysop.
<2> "Telink Protocol"
---------------------
Telink Protocol is a system of file transfer that allows batch
files to be used. With Telink Protocol you can set your
communications program to receive/transmit any number of files
unattended. Currently Colossus does not support Telink Protocol,
but it will be put in within the next version. This parameter
can remain set to "Yes". Until the protocol is implemented, it
makes no difference.
<3> "Colossus Node Number"
--------------------------
When you receive Colossus, a Node Number will be assigned to
you. With this Node Number, you will be able to send/receive
mail from other Colossus BBS Systems. If you set your Node
-30-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
Number to something other than what is assigned to you, your
board will be excluded from receiving or sending Colossus
Networking Mail. Set this parameter to the Node Number that is
given to you. (See section 7.0)
<4> "Colossus Net Number"
-------------------------
When you receive Colossus, you are also assigned a Net Number.
Set this parameter to the Net & Node Number that is assigned to
you. (See section 7.0)
<5> "Alternate Node Number"
---------------------------
Since Colossus has a Net Number within the Fido Network, Fido
BBS sysops can send mail to Colossus Boards. If you were
running a Fido board before you switched to Colossus, you can
still keep your Fido Node/Net Numbers. That way, you can still
receive mail from the other Fido Boards. To keep your Fido Node
Number, just put it as the Alternate Node Number. Same holds
true for the Alternate Net Number, place your Fido Net Number in
as your Colossus Alternate Net Number.
<6> "Alternate Net Number"
--------------------------
See above.
<7> "Long Distance Calls"
-------------------------
If you would rather Colossus NOT make long distance calls to
other Colossus Boards when it sends Net-Mail, then set this
parameter to "No". But if you would like Colossus to make long
distance calls during the sending of Net-Mail, then set this
parameter to "Yes". Remember: Long distance calls cost money!
<8> "All messages must be public"
---------------------------------
If you want your complete message area to be public, and NOT
allow private messages you can toggle it here.
<9> "Security For Assistant Sysops"
-----------------------------------
If you want selected individuals to be able to read sysop
messages as well as private messages left from user to user, you
may set the security level required here. Any caller with this
security level, or greater, will then be able to read those
messages. For example, with the security level set to 50,
callers with a security level of 50 (or greater) would be able
to read all the sysop messages and all private messages. This
is ideal for allowing assistant sysops to help monitor your
message base.
(NOTE: The "chief" sysop of a Colossus system requires a
security level of 100 or higher. A three-digit security
level permits access to a far greater range of sysop
maintenance utilities and should be assigned to anyone
other than yourself with extreme caution.)
-31-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<A> "300 Baud result codes"
---------------------------
Enter the number or character your modem will return when
connected at 300 baud.
<B> "1200 Baud result codes"
----------------------------
Enter the number or character your modem will return when
connected at 1200 baud.
<C> "2400 Baud result codes"
----------------------------
Enter the number or character your modem will return when
connected at 2400 baud.
<D> "Output filename for the automatic Call Analyzer"
-----------------------------------------------------
This may be any legal filename for Colossus to write the Call
Analyzer information to. One choice would be a bulletin file;
this way the bulletin could be updated automatically.
*W* ALT+G (Set Caller Number & Board Start Date)
----------------------------------------------
If you were running different board software before you began to
run Colossus, you can set your Number of Callers back to what it
should be instead of starting over again at 0 [ugh!]. Or if
you erase your SYSINFO.000 (where your Caller Number is kept),
you can use ALT+G to set it back to what it was. Simply invoke
ALT+G and then enter your Caller Number to do this. This
function will also ask for the original Start Date of your
board. You may enter any sting up to 20 characters.
*A* ALT+K (Keyboard Toggle)
-----------------------
This ALT+Key allows the sysop to prevent any characters from
appearing on the screen if the sysop accidentally presses some
keys. If activated, the word "Kybd" will appear at the 5-line
window on the bottom of your monitor, and all characters will be
allowed to appear on your and the users screens. If NOT
activated, the word Kybd will NOT be present at the 5-line
window, and all characters typed at your console will be
filtered out and will not appear on your or the users' screens.
*O* ALT+N (Upgrade Security on line)
--------------------------------
If you have a caller online and you wish to change their
Security level, you may do so with this command. Their new
Security level becomes permanent when they log-off, therefore if
you want to give them the higher access for just a short period
of time, lower their security level before they log off. The
caller is unable to see you make any of these changes!
-32-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
ALT+S (Sysop sign-on/next)
--------------------------
This ALT+Key can be used is two ways:
<1> If you wish to sign-on the system as the sysop.
<2> If a user is using the system and you wish to sign-on next,
after he logs off. If you use this while a user is online
and you change your mind, simply press ALT+S again to abort.
*O* ALT+A (Screen dump & Caller Lockout)
-------------------------------------
If you have a problem caller, whether it be a Security problem
or just a pest, you can send the contents of a file called
"Alt-A.BBS to the screen and then perform a permanent lockout.
*A* ALT+R (System Status Report)
----------------------------
Colossus is the only Bulletin Board software which displays to
the sysop, at any time, a complete system status report which is
in real time, updated every minute of every hour of every day.
The System status is displayed as follows:
--- System Status Report ---
Number of minutes since system reset . . . . . .1000
Number of minutes of actual system use . . . . .500
Total system operating efficiency . . . . . .50%
Number of minutes since last caller logged on . . .10
Total Number of callers since system reset . . . .17
Number of 300 baud callers. . . . . . . . .8
Number of 1200 baud callers . . . . . . . .6
Number of 2400 baud callers . . . . . . . .3
Total number of messages left . . . . . . . .7
Total number of comments left . . . . . . . .12
Total number of files uploaded . . . . . . . .3
Total number of files downloaded . . . . . . .17
Total number of kilobytes uploaded. . . . . . .20
Total number of kilobytes downloaded . . . . . .600
Last callers's name. . . . . . . . . .Rick Heming
I'm sure you'll find this one of your most used utilities. You
may pop this window up anytime, even when a caller is online.
-33-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
10.0 EXTENDED KEYS EXPLAINED
Colossus also has some special "extended" keys for special use
by the sysop.
10.1 AVAILABLE KEYS
"Home" - Displays a help Screen
"PageDn" - Extended User Statistics
10.2 EXTENDED KEYS AVAILABLE
"Home Key"
-----------
Displays a quick summary of all of the keys available to the
sysop.
"PageDn"
----------
Displays extended user statistics when a caller is online.
-34-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
11.0 THE SCHEDULER
This section explains scheduled events in greater detail.
11.1 HOW TO ACCESS THE SCHEDULER
The scheduler is accessed from the update menu. <1> will list
the schedule events; <2> will create an event; and <3> will
Remove, Disable, or Enable.
11.2 SCHEDULES EXPLAINED
Schedule "A"
------------
Schedule A will invoke the Net-Mail option. This schedule
should be set to run in the national net-mail time slot of 1am
Pacific time, 4am Eastern time. The window length should be 60
minutes and should be set to run every day.
Schedule "X"
------------
This schedule allows you to automatically Drop to DOS. This is
done and Colossus will set the ERRORLEVEL to 32. You must have
IF ERRORLEVEL 32 FILENAME.BAT in your C.BAT file. FILENAME.BAT
then must call C.BAT when it's finished to bring Colossus back
up.
Schedule "Y"
------------
Schedule Y is the Call Analyzer. Be sure to name the file you
want it to write to in the configuration menu (ALT+F). The
window length should be 2 minutes.
Schedule "Z"
------------
This schedule will automatically pack your message base for you.
This is just like compacting then from the Sysop Menu.
-35-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
12.0 MAIN MENU EXPLAINED
The Main Menu is the first focal point your callers will arrive
at after they have visited the Bulletins (that is, if your board
supports bulletins). For the purpose of discussion, each menu
displayed will be as if the sysop (with the highest security
level) was viewing it. In this case the main menu would look
like this:
12.1 MAIN MENU EXAMPLE
Main Menu:
<B>ulletins <E>ditorial
<C>omments to the sysop <G>oodbye and logoff
<F>iles section <L>ocate a User
<I>nitial welcome message <O>nline Programs
<M>essage section <Q>uestionnaire
<P>age the Sysop <U>tilities for the Sysop
<S>tatistics <#>List active users
<X>pert toggle <?>Help with Commands
<!>User Status
12.2 EXPLANATION
Above are all the possible selections available. Remember,
these menus are dynamically built. That means a caller will
only see the options available to them, as defined in MAIN.MNU
by their security level. (Review section 3.3)
<B>ulletins:
Access files BULLETINS.BBS and BULLET1, BULLET2, etc. These are
normal ASCII files containing information pertinent to your
board's topics, location and theme. BULLETIN.BBS is the main
bulletin file listing all of the bulletins available. If the
file is absent, the "No bulletins available" is displayed when
the user accesses it.
<C>omment to the Sysop:
This feature allows the caller to leave private messages to the
sysop. It has the same look at the message entry, however the
output is appended into an ASCII file called COMMENTS.BBS. (If
the file is not present Colossus creates it.) This file can be
read from the Sysop Menu, or you can drop to DOS (ALT+D) and
copy it to your printer.
<F>ile Section:
Transfers callers to the File Menu.
<I>nitial Welcome Message:
Dumps the file WELCOME1.BBS back to the screen.
<M>essage Section:
Transfers callers to the Message Menu.
-36-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<P>age the Sysop:
Pages the sysop for 20 seconds if the sysop has his page
function (F4) on. If the function is OFF, the caller receives a
"Sysop not available" message.
<S>tatistics:
Displays the date Colossus first started running, number of
messages currently in the message area, and the current system
date and time.
<X>pert toggle:
Displays shorter menus for experienced callers.
<E>ditorial:
Displays the contents of EDTORIAL.BBS to the screen.
<G>oodbye & Logoff:
Displays the file GOODBYE.BBS and drops DTR.
<L>ocate a user:
Searches to see if the name entered is in the users log.
<O>nline Programs:
This one requires some explanation. First, make sure
COMMAND.COM is located in the main Colossus directory, along
with the file SHELL.BBS, which is the ASCII file displayed to
the screen when <O> is selected. SHELL.BBS may contain
information about the programs available for use. Note the
PROGRAM NAMES MUST BE IN ALL CAPITAL LETTERS (e.g.,
PC-WRITE.EXE, ADVENT.EXE, ETC.) Colossus will drop into DOS,
load the program selected and execute the program. Note
however, Colossus will not redirect the video or keyboard input
or output. Therefore, at present this function will not work
for remote callers, but will work if signed on locally. We're
hoping some of you can help us write a routine which will
redirect the video and keyboard input before the program is
executed. Any takers?
<Q>uestionnaire:
Invokes the questionnaire, QUESTION.BBS. Answers are placed in
the file called ANSWERS.BBS. You must drop to DOS (ALT+D) to
read these answers using either the TYPE or COPY command.
<U>tilities for the Sysop:
Transfers callers to the Sysop Menu.
<#>List active users:
Displays users' names, last date & time called, and city and
state they reside.
-37-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<?>Help with commands:
Displays MAIN.HLP which contains a brief explanation of all the
commands.
<!>User Status:
Allows the caller to change his password or location, and view
their vital statistics.
-38-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
13.0 MESSAGE MENU (MMS) EXPLAINED
The Message Menu is the point from which your callers take part
in mail interaction. The first time they visit this area
Colossus will check to see if they have any NEW messages since
there last date called. If they do, Colossus will ask them if
they wish their mail to be MARKED for reading later. If the
caller selects this option, call their mail is flagged, and when
they select the <R>ead messages function, they may select
<M>arked and read those messages first, skipping everything in
between.
Colossus also displays the highest message the caller has read,
plus the total number of messages available.
13.1 MESSAGE MENU EXAMPLE
Message Menu:
<C>HANGE BOARD <R>EAD MESSAGES
<F>ast Scan Messages <S>can Messages
<E>NTER A MESSAGE <L>IST & CHECK ALL MAIL
<K>ill a Message <T>ext Search
<Q>uit to MAIN MENU <G>oodBye
<X>pert mode toggle <?>HELP WITH COMMANDS
13.2 MESSAGE MENU EXPLANATION
<C>HANGE BOARD:
Allows the caller to move from one message area to another, or
to select ALL BOARDS which will allow them to read from every
board they have access too.
<F>ast Scan Messages:
Displays the message number, description, and board number
assigned to each message.
<E>NTER A MESSAGE:
Prompts the caller to enter a message.
<K>ill a message:
Requests message number to kill and marks that message for
deletion.
<Q>uit to MAIN MENU:
Transfers caller to the Main Menu.
<X>pert mode toggle:
Toggles expert mode on/off.
-39-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<R>EAD MESSAGES:
Requests message number to start reading from. Reads only the
messages in the current message section unless the caller has
switched to ALL BOARDS.
<S>can Messages:
Scans message number, date written, to, from, subject, and board
number.
<L>IST & CHECK ALL MAIL:
Starts at message number 1 and displays all the messages has
addressed to the caller or written by him. Messages are also
marked for quick retrieval.
<T>ext Search:
Search for matching text in the Name or Subject of a message.
<G>oodBye:
Displays GOODBYE.BBS and drops DTR.
<?>HELP WITH COMMANDS:
Displays MMS.HLP to the screen.
13.3 SPECIAL COMMANDS FOR SYSOP STATUS
The Message section has a few "Special Commands" for sysop-
privileged users.
It's important to note that only the sender and receiver can
"Kill" messages, except for users with sysop security
privileges, who can read and kill any messages.
Next is the <M>ove command. Sysops can also move a message to
another board area. This is a great feature and comes in handy
when a caller leaves a message in the wrong board. Just be sure
not to move a general message to the Net-Mail area, and make
sure you're moving the message to a board area that actually
exists!
Lastly is the <U>ndelete command. Anyone with sysop privileges
will automatically be able to read all the messages in the
message system, even if they have been deleted. If you see a
message which has been marked for deletion you may UN-DELETE it
by using this command. Your callers will not be able to read
deleted messages unless their access level is considered sysop
level.
-40-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
14.0 FILE MENU EXPLAINED
The file area is one of the most active areas on a bulletin
board. Colossus currently supports 3 file transfer protocols:
1) Xmodem, 2) Xmodem/CRC, and 3) ASCII.
We hope to add several more protocols in the future as Colossus
is developed.
14.1 FILE MENU EXAMPLE
File Menu:
<C>HANGE FILES AREA <L>IST FILES
<S>tatistics of Files <G>oodbye
<D>OWNLOAD FILES <U>PLOAD FILES
<X>pert Toggle <?>Help with Commands
<N>ew Files Search <M>atch on File Name or Desc.
<H>elp Downloading/Uploading <Q>uit to MAIN MENU
14.2 EXPLANATION
<C>HANGE FILE AREA:
Prompts the caller to change from the current file area, or
press the ENTER key to list the areas they have access to.
<S>tatistics of Files:
Displays the available disk space for uploads, total number of
Upload & Download kilobytes. Also, if the caller has uploaded
any files, Colossus will display the ratio of Uploads to
Downloads.
<D>OWNLOAD FILES:
Prompts the caller for the download file name, checks to see if
it's in the current file area, requests the transfer protocol,
then displays the number of blocks and estimated time for the
download to be completed.
<X>pert Toggle:
Toggles expert mode on/off.
<H>elp Downloading/Uploading:
Displays the file PROTOCOL.HLP which gives detailed instructions
for uploads and downloads. PROTOCOL.HLP was written by Rick
Heming (KernCom).
<L>IST FILES:
Displays the file FILES.BBS listed in the current file area.
This file is also appended if this is the path on an upload.
<G>oodbye:
Displays GOODBYE.BBS and drops DTR.
-41-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<U>PLOAD FILES:
Prompts the caller for the Upload file name. If the file is
found the caller is told "File is already cataloged". If not,
Colossus requests a transfer protocol and sets up to receive the
file. Upon successful receipt, the caller is prompted for a
file description which is append to FILES.BBS assign to that
Upload path.
<?>Help with commands:
Displays the contents of FILES.HLP.
<N>ew Files Search:
This is a super fast routine which searches for files added
since the caller's last time on. The caller may also enter a
date for the search to start with. In any event, the date
entered or last late date on is compared with the date listed in
FILES.BBS starting with character #24. Note the format should
be as follows:
0---------1---------2---|-----3---------4---------5-------6..8
FILENAME.EXT 100,000 12-15-85 Description of the file....
<M>atch of File Name or Desc.:
This is another search function which is used when your callers
want to see if a particular file is on your system. The string
your callers enter is checked to see if it appears anywhere on
the File Data Line. If a match is found, the entire line is
displayed.
<Q>uit to MAIN MENU:
Transfer to the Main Menu.
-42-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
15.0 SYSOP MENU EXPLAINED
Almost all the sysop utilities are contained in Colossus. No
external programs are need to do normal, day-to-day maintenance.
15.1 SYSOP MENU EXAMPLE
Sysop Menu:
<1>List active events <2>Create events
<3>Update Events <4>Update system files
<5>Modify users <6>List Comments
<7>List Callers Log <8>Pack users file
<9>Pack Messages files <A>Delete Comments
<B>Delete Callers file <D>rop to DOS
<P>rint Users File <Q>uit to MAIN MENU
<?>Help!
15.2 EXPLANATION
<1>List active events:
Lists the current events set in the scheduler. Displays the
event number, starting time, window length, schedule letter
designation, and displays whether it is ENABLED or DISABLED.
<2>Create events:
Colossus is a time driven program. One of Colossus's main goals
is to be maintenance free (or require very little upkeep on the
part of the sysop). The scheduler is the function which keeps
track of all the duties to be perform.
When you select this function, Colossus will prompt you for the
event number. These numbers must be in chronological order
(i.e., 1,2,3,4, etc..). After you have selected a number,
you'll need to enter the starting time. This time MUST BE
ENTERED IN MILITARY TIME with the hour and minutes separated by
a colon. For example 3:15pm would be entered as 15:15, or
4:00am would be entered as 04:00.
Next Colossus will ask for the Window length. Simply put, this
is the time you would like the event to last in MINUTES. So a
Window length of 60 minutes would be entered as 60.
Next you need to tell Colossus which days you want the event to
happen. You may select Monday thru Sunday or All. Below is the
chart for easy reference:
0 = MONDAY 2 = WEDNESDAY 4 = FRIDAY 6 = SUNDAY
1 = TUESDAY 3 = THURSDAY 5 = SATURDAY 7 = ALL DAYS
Last is the scheduled event (A..Z). As of this writing, the
following events may be activated:
SCHEDULE "A" : Net-Mail (See section 7.0)
SCHEDULE "X" : Halt, set Errorlevel to 32.
-43-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
SCHEDULE "Y" : Run the Call Analyzer Report.
SCHEDULE "Z" : Auto Pack Messages, invokes the pack
messages routine, the same as #9 from
the Sysop Menu.
SEE SECTION 11.0 ON "SCHEDULES"
<3>Update Events:
Allows you to update events which have ALREADY been created.
You may Enable, Disable, or Remove an event, and also quit.
Your choice is displayed as <E>nable, <D>isable, <R>emove,
<Q>uit.
<4>Update system files:
See section 5.3 "Setting up the System Files".
<5>Modify users:
This is the area where you'll perform most of your Sysop
Maintenance. When you select this function, your first user
record is displayed. The format is as follows:
#1 Name : SYSOP
From $ : Bakersfield, CA
Password : GreatProgram
Phone :
TimesOn : 5
Credit : 0 Pending : 0
Downloads : 4 Uploads : 2
Last Called : 9 Nov 85 15:10
Security : 50
Search : <R>ecord, <F>ind, <Q>uit
Change :
<N>ame,<1>From,<P>assword,<T>elephone,<C>redit,<S>ecurity
Toggle : <L>ock Out, <D>elete
Choice : ?
<R>ecord ---- Jumps to that record position
<F>ind ----- find a caller's record. Enter both First & Last
Name
<Q>uit ----- return to the Sysop Menu
<N>ame ----- is used to change the caller's name.
<1>From ----- City, State they're Calling From
<P>assword -- is for changing a caller's password
<T>elephone - If /P is used.
<C>redit ---- credits a caller's account used for Net-Mail
transactions.
<S>ecurity -- change a caller's security level
<L>ock ----- toggle a caller for lockout
<D>el ------ is used to mark a caller for deletion
<6>List Comments:
List comments left by callers from the Main Menu.
-44-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<7>List Callers Log:
Displays the most recent caller's logon, and activity.
<8>Pack users file:
Packs the user file. Purges the callers marked for deletion.
<9>Pack Messages files:
Packs the message file. Purges the messages marked as killed.
<A>Delete Comments:
Deletes the Comments file.
<B>Delete Callers file:
Deletes the Callers log.
<D>rop to DOS:
Used only for remote sysop. For extra security protection, you
MUST have /W on the Colossus command line to allow dropping to
DOS. When invoked, Colossus calls up a batch file called
"REMOTE.BAT" which should contain the following:
CTTY COM1
ECHO Welcome to Colossus Drop into DOS Function
ECHO Return to your Colossus Root Directory and...
ECHO Type C.BAT to return to Colossus
Be sure your C.BAT file contains "CTTY CON" as the first
statement and that COMMAND.COM is in your main Colossus
directory. To return to Colossus, be sure to return to the main
Colossus directory and type the word "C.BAT"
<Q>uit to MAIN MENU:
Returns you to the Main Menu.
<P>rint Users File:
Prints the callers file to the printer. Be sure to have your
printer toggle "Lptr" light on.
<?>Help!
Displays the contents of the file "SYSOP.HLP"
-45-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
16.0 THE SYSOP'S "UPDATE" MENU EXPLAINED
The Update Menu is mainly used in setting up Colossus for the
first time or changing some of your board's Message and Files
areas. Once you have set up a few areas, it will all fall into
place.
16.1 UPDATE MENU EXAMPLE
Update Menu:
<A>Net message system toggle <B>Net file system toggle
<C>reate/read a system file <D>ownload file path
<F>ile security <I>Message Description
<J>File Description <L>ist system file
<M>essage security <Q>uit to MAIN MENU
<S>ave system file <U>pload Path
16.2 EXPLANATION
<A>Net message system toggle:
When a message area is used as your Net-Mail section, this
function will flag the message area for Net-Mail transactions.
When a message area is flagged as the Net-Mail section, a "*"
will be placed next to the Message Description when the boards
are listed from the Message Menu. This function will place the
comment "Net Message Area" under the system record when listed.
<B>Net file system toggle:
At this time Colossus doesn't support files transfers in the Net
System. The file transfer "Telink" is currently in development
by the Forbin Project, and once finished will allow automatic
files transfers between Colossus Nodes. It will also allow
automatic Uploads and Downloads (*.*) between Colossus and
Qmodem.
<C>reate/read a system file:
This function allows you either to create or read a system file.
Note System Files contain the following information:
System Record #1
Message security..
File security.....
Upload Path.......
Download Path.....
Msg description...
File description..
If the Message or File area is flagged as the Net Section, the
following comments will be placed at the end of the System
record:
Message Net Area
File Net Area
-46-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
<D>ownload file path:
Is the path where Colossus will look for the files described in
the file description. For example, if you're using a hard disk
and the Colossus files are listed in a sub-directory called
"\COLOSSUS" and all the games are in a sub-directory called
"\COLOSSUS\GAMES" your download path would be C:\COLOSSUS\GAMES.
<F>ile security:
Minimum security level required to access (and see) the file
area associated with this system record.
<I>Message Description:
Description of the message area associated with the system
record.
<J>File Description:
Description of the file area associated the this system record.
<L>ist system file:
This function will display the current system record.
<M>essage security:
Minimum security level to access (and see) this message area
associated with this system record.
<Q>uit to SYSOP MENU:
Return to the Sysop Menu.
<S>ave system file:
Very important. If you change a system record, YOU MUST SAVE
YOUR CHANGES before you change system records or return to the
Sysop Menu.
<U>pload Path:
Any legal DOS Path you would like your uploads directed to.
-47-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
17.0 COLOSSUS TECHNICAL REFERENCE INFORMATION
We do not plan on releasing the source code for Colossus,
however we do feel some information may be of use to our sysops
to help them understand how Colossus works, and how it handles
certain routines. If there is something you would like to know
which is not covered in the documentation, please drop us a
message via Net-Mail to Colossus Country 200/3. We'll consider
adding the information to this section.
17.1 RECORD STRUCTURE FOR "USERS.BBS"
USER.BBS contains the following record structure:
Type
Users = Record
UserName : String[37]; { Users name }
CallingFrom : String[30]; { location }
Password : String[14]; { Password }
TimeDate : String[17]; { Last time called }
PhoneNumber : String[12]; { User phone number }
Credit, { Credit limit }
Pending, { Charges pending }
SecurityLevel, { Security level }
Uploads, { Number of ULoads }
Downloads, { Number of DLoads }
TotalUK, { Total K uploaded }
TotalDK, { Total K downlded }
TimesOn, { Number times on }
TimeLeft, { Time left today }
Last_Read, { Last message read }
Last_M_Area, { Last message area }
Last_F_Area: Integer; { Last file area }
Xpert, { Xpert toggle }
LockedOut, { allowed user? }
Deleted, { Mark for deletion }
Universal : Boolean; { All Boards Selected }
Graphics_Wanted : Byte ; { Type of Graphics }
Extra:Array[1..20] of Integer;{ Extra Space }
End;
-48-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
18.0 SUPPORT PROGRAMS FOR COLOSSUS
As Colossus continues to mature, we hope to see continued
support by our sysops and program developers. Listed below are
programs which were written to support the Colossus Bulletin
Board Program. We would like you to know of their existence,
and thank the developers for their time and effort to support
our cause.
18.1 MERGER
Author : Tom Neff
Board : Atlantic Palisades (200/7)
Overview:
MERGER is a program that "sweeps" through your Colossus file
areas and lets you perform actions on each one -- move, kill,
rename, copy, change description, etc. Just pick a file area
and then type ? for a list of the commands.
You can rebuild FILES.BBS from scratch, Sort lines (with the O
command) your choice of two different ways! <A>lpha sorts
INCREASING with the whole line as the key; <N>ewest sorts
DECREASING on date, then INCREASING on filename. This places
the newest files first, which lets you see what's been posted
lately without having to give a specific date in Colossus' New
command. The Sort command sorts from the CURRENT line to the
end of FILES.BBS, so you can preserve your banner at the top --
just skip down to the first file line and type <O>.
Also new with 0.9! Mini CHAT mode, so remote and local sysops
can argue with each other about where to put that new
combination checkbook balancer and disk speed test program!
Type ! to get there, Ctrl-Z to get back out.
And much, much more. Merger can run from either stand-alone or
from <O>nline programs. Tom includes a super help file to get
you started. This program is a must!
18.2 RBBS2COL
Author : Jim Harrer
Board : Colossus Country
Overview:
This program converts RBBS 12.5 (and Greater) Users files over
to Colossus 1.10 format. This program helps sysops running RBBS
to convert to (the faster) Colossus without making their Users
go through the re-logon procedure.
-49-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
18.3 CALLRPT
Author : Jim Harrer
Board : Colossus Country
Overview:
The Call Reporter reads the Colossus CALLERS.LOG and dumps the
statistical information to either the printer, a file, or both.
This is a great way to recap your board's activities. This
program was incorporated into the Colossus scheduler beginning
with version 1.10.
-50-
COLOSSUS BULLETIN BOARD SOFTWARE DECEMBER 29,1985
19.0 LATEST COLOSSUS UPDATES
Because Colossus is growing so fast, we have set up just a few
boards where you'll be able to get Revisions & Updates. As the
Colossus family grows, we're sure this list will grow, also!
New versions of Colossus are released up to 4 times a month on
Sunday Evenings at 6pm (Pacific Standard Time). You can check
with the Beta Tester closest to you for the most recent version.
Send all net mail concerning bugs, suggestions and comments to:
Colossus Committee, Colossus Country, net 200, node 3.
19.1 COLOSSUS PROGRAM UPDATES
The latest Colossus Program & Overlays can be obtained from:
Board Name Sysop Number Location
---------- ----- ------ --------
Colossus Country Jim Harrer 805/399-1329 Bakersfield, CA
The Forbin Project John Friel III 319/277-0040 Cedar Falls, IO
Kerncom Rick Heming 805/833-0359 Bakersfield, CA
E N D O F F I L E
-51-